Skip to content

improvement/CLDSRV-451-specific-7.70-apis-update#5495

Merged
bert-e merged 2 commits intodevelopment/7.70from
improvement/CLDSRV-451-specific-7.70-apis-update
Dec 15, 2023
Merged

improvement/CLDSRV-451-specific-7.70-apis-update#5495
bert-e merged 2 commits intodevelopment/7.70from
improvement/CLDSRV-451-specific-7.70-apis-update

Conversation

@benzekrimaha
Copy link
Contributor

@benzekrimaha benzekrimaha commented Dec 14, 2023

Bucket policies are not correctly interpreted, this is part of the following epic to fix that: scality/Arsenal#2181

This PR is aiming to update get apis since object and bucket authorisations are made at API level and need to support implicit denies, ticket linked to this issue here : https://scality.atlassian.net/browse/CLDSRV-451

PRs providing implicit Deny logic to CS for processing in this PR
scality/Arsenal#2181 and scality/Arsenal#2193
https://github.com/scality/Vault/pull/2135
#5322
#5420
#5432
#5456
#5462
#5470
#5479

Here CI links for zenko tests :

As there are differences on the 8.x branches reviews are highly appreciated

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Hello benzekrimaha,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Incorrect fix version

The Fix Version/s in issue CLDSRV-451 contains:

  • 7.70.11.3

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 7.70.36

  • 8.6.17

  • 8.7.37

  • 8.8.11

Please check the Fix Version/s of CLDSRV-451, or the target
branch of this pull request.

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@scality scality deleted a comment from bert-e Dec 14, 2023
@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update with contents from improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.6.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.6
 $ git merge origin/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@benzekrimaha benzekrimaha changed the title CLDSRV-451: updating buckettagging apis for impDeny improvement/CLDSRV-451-specific-7.70-apis-update Dec 14, 2023
@benzekrimaha benzekrimaha force-pushed the improvement/CLDSRV-451-specific-7.70-apis-update branch from 5fdb2b0 to 836fc80 Compare December 14, 2023 15:58
@benzekrimaha
Copy link
Contributor Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update with contents from improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.6.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.6
 $ git merge origin/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update with contents from w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.7.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.7
 $ git merge origin/w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update with contents from w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.8.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.8
 $ git merge origin/w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

/reset

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Lossy reset warning

There seems to be manual commits on integration branches (e.g. conflict
resolutions) that will be lost if you chose to reset.

You can use the force_reset command if you still want me
to delete those branches.

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

@bert-e force_reset

@scality scality deleted a comment from bert-e Dec 14, 2023
@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Reset complete

I have successfully deleted this pull request's integration branches.

The following options are set: create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update with contents from improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.6.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.6
 $ git merge origin/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update with contents from w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.7.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.7
 $ git merge origin/w/8.6/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Conflict

A conflict has been raised during the creation of
integration branch w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update with contents from w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update
and development/8.8.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 $ git fetch
 $ git checkout -B w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update origin/development/8.8
 $ git merge origin/w/8.7/improvement/CLDSRV-451-specific-7.70-apis-update
 $ # <intense conflict resolution>
 $ git commit
 $ git push -u origin w/8.8/improvement/CLDSRV-451-specific-7.70-apis-update

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@benzekrimaha
Copy link
Contributor Author

/create_pull_requests

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4

Follow integration pull requests if you would like to be notified of
build statuses by email.

The following options are set: create_pull_requests, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_pull_requests, create_integration_branches

Copy link
Contributor

@anurag4DSB anurag4DSB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reveiwed integration branch #5497 (review)
there are new changes in the merge commit for metadataSearch, object Restore and routeveeam

@anurag4DSB
Copy link
Contributor

Integration tests used: #5496

Copy link
Contributor

@anurag4DSB anurag4DSB left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

adding a blocker for merge as author will be OOO tomorrow and we need author approval

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following reviewers are expecting changes from the author, or must review again:

The following options are set: create_pull_requests, create_integration_branches

@anurag4DSB anurag4DSB dismissed their stale review December 14, 2023 17:26

ok to merge, we found the issue.

@bert-e
Copy link
Contributor

bert-e commented Dec 14, 2023

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_pull_requests, create_integration_branches

@benzekrimaha
Copy link
Contributor Author

@bert-e approve

@bert-e
Copy link
Contributor

bert-e commented Dec 15, 2023

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/7.70

  • ✔️ development/8.6

  • ✔️ development/8.7

  • ✔️ development/8.8

The following branches will NOT be impacted:

  • development/7.10
  • development/7.4

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve, create_pull_requests, create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Dec 15, 2023

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/7.70

  • ✔️ development/8.6

  • ✔️ development/8.7

  • ✔️ development/8.8

The following branches have NOT changed:

  • development/7.10
  • development/7.4

Please check the status of the associated issue CLDSRV-451.

Goodbye benzekrimaha.

@bert-e bert-e merged commit 126ca35 into development/7.70 Dec 15, 2023
@bert-e bert-e deleted the improvement/CLDSRV-451-specific-7.70-apis-update branch December 15, 2023 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

Comments